id: pattern-work title: Pattern Work meta: How to manage the pattern, transitions and flight of xx when operating a tower facility within Infinite Flight. order: 4 #
Pattern Work #
The traffic pattern is a standard flight path followed by aircraft when taking-off and landing while maintaining visual contact with the airport. In Infinite Flight the pattern altitude is 1000ft AAL (above aerodrome level) for prop aircraft, and 1500ft AAL for jet aircraft. It consists of multiple legs, each being joined by a 90 degree turn, and these are shown in the image below:
Manual
: For Pattern Work to be allowed, Visual Meteorological Conditions (VMC) must{.red} exist, aircraft must{.red} be able to fly a standard pattern and traffic levels need to be manageable. More info?
For a step by step guide on how to issue pattern entries, sequencing and clearances, make sure to check out the Inbounds page.
+++ SCENARIO - Re-Sequencing
::: scenario-heading Scenario :::
::: scenario I-DRUM and N1DC have both already been sequenced and cleared for RWY05L. As both aircraft continue downwind, I-DRUM has gone further downwind than the Controller expected. :::
{.scenario}
| Technique 1 |
|---|
| 1: Re-clear N1DC as number 1 |
| 2: Re-sequence I-DRUM as number 2 |
| 3: If you are concerned about separation, you can tell I-DRUM to “extend downwind, I’ll call your base” to alleviate this |
{.technique}
| Technique 1 | Pro or Con? |
|---|---|
| :fa-check-circle: | Efficient |
| :fa-check-circle: | Greater Pilot satisfaction |
| :fa-times-circle: | May increase workload as you have to send various commands |
{.prosandcons}
| Technique 2 |
|---|
| 1: Instruct I-DRUM to “turn base” |
| 2: This will force I-DRUM to fly a tighter pattern |
{.technique}
| Technique 2 | Pro or Con? |
|---|---|
| :fa-check-circle: | Can be efficient |
| :fa-times-circle: | Some pilots/aircraft may not be able to fly as tight a pattern |
{.prosandcons}
+++
Transitions #
Transitions can be requested by aircraft when they are not with a radar facility and are transiting through the tower controller’s airspace. For Infinite Flight, Tower airspace is defined as the most immediate ring/boundary surrounding the airport and up to 5000ft AAL (therefore if the elevation of the airport is 1000ft, the tower’s airspace would be 1000ft – 6000ft).
Manual
: A transition must{.red} only be approved within tower’s airspace (so in the example above, no higher than 6000ft). Separation must{.red} be applied if the Tower Controller has aircraft in the pattern. More info?
Step 1
: When an aircraft requests a transition, the aircraft symbol will flash amber on the map as well as their callsign on the flight progress strip
Step 2
: Either tap the aircraft on the map (and then “Other Message”), or the flight progress strip to bring up the communication menu
Step 3
: Determine an altitude that will keep the aircraft within tower’s airspace, but also provide separation with traffic that may be in the pattern
Step 4
: Tap “Respond to Transition > [select <10,000ft / >=10,000ft ] > [select altitude]”
Tip
: A minimum of 500ft is required between VFR traffic however we recommend giving a transition that provides a minimum of 1000ft separation to satisfy IFR requirements too!
Flight of XX #
Manual
: When controlling aircraft using the “Flight of XX” callsign, you must{.red} only send commands to the lead aircraft and treat the flight of xx as one aircraft. More info?
Step 1
: When the lead aircraft makes a request, the aircraft symbol will flash amber on the map as well as their callsign on the flight progress strip
Step 2
: Either tap the aircraft on the map (and then “Other Message”), or the flight progress strip to bring up the communication menu
Tip
: It may be easier to use the flight progress strip as multiple aircraft flying in formation can make tapping the aircraft on the map a bit tricky!